Creating a screen flow

You can use a screen flow to collect information from a single user. By using a flow that defines routing logic in one shape instead of many connectors, you can quickly add functionality to your application.

1. Create the rule that stores the screen flow by performing the following steps:

   1. In the header of Designer Studio, click + Create > Process > Flow.

   2. On the Create form, enter values in the fields to define the context of the screen flow.

      Options include:

      • Label — Describes the purpose of the flow.

      • Apply to — Applies a scope to the flow, by associating the flow with a class and its inherited classes.

        The class controls which rules the flow can use. It also controls which rules can call the flow.

      • Add to ruleset — Identifies the name and unlocked version of a ruleset that stores the flow.

      • Identifier — Creates a unique identifier for the flow.

        You can keep the default value or click Edit to manually define an identifier.

   3. Click View additional configuration options.

   4. Click Standard template for screen flows.

   5. Click Create and open to open a screen flow that contains the Start shape, the Assignment shape, and the End shape.

2. In the flow diagram, double-click the Start shape to open the property panel.

3. Define how the user interacts with the screen flow at run time, by entering values in the fields.

   Options include:

   • Harness — Defines the presentation of the screen flow.

     For example, you can display the steps in the screen flow as tabs or as nodes in a tree.

   • Save on last step — Saves the case after all steps in the screen flow are completed.

     If you do not select this option, the case is saved each time that the user completes an assignment.

   • Allow errors — Allows users to move the screen flow to a different step, even if the current step fails validation.

     This option is available only when you select the Save on last step check box.

   • Router — Determines how assignments in the screen flow are routed to a worklist.

     For example, you can select the standard ToDecisionTree activity to route assignments based on the value that is returned by a decision tree.

     To route assignments to a work queue instead of a worklist, you must configure an assignment in the flow that calls this screen flow.

4. Click Submit.

5. Configure the Assignment shape with a task that the user performs.

6. Optional: To enhance your screen flow, add and connect more shapes.

You can test your flow by running it or calling it from a subprocess in the life cycle of a case.

Open topic with navigation